BOM Common Bill of Materials Upload

Description

BOM Common Bill of Materials Upload creates common bills of material in one or more target organizations that reference the bills of a source (master) organization, so the target assemblies share the source bill rather than holding a copy. The download lists one row per bill and target organization, with columns showing whether each target is ready; you flag the rows to process and upload. Sub-assembly and substitute-item bills that the target organization does not have yet are made common in the same step.

When to use it

  • Share bills maintained in the master organization with its child organizations instead of keeping independent copies.
  • Set up the bills of a new organization in bulk during a rollout.
  • Make a whole bill structure common at once, including its sub-assembly and substitute-item bills, which Oracle’s Create Common Bill otherwise requires one by one.
  • Check, per target organization, which assemblies already have a bill or are missing item assignments before committing.

Before you start

  • The source organization is an item master organization with bills of material; the target organizations use it as their master organization.
  • Your responsibility has access to the target organizations. Organizations it cannot access are not listed, so the download is empty if it reaches none of them.
  • The assembly item and all component and substitute items of the bill structure are assigned to the target organization.

Choose a template

TemplateUse it for
Common BOM Upload Template (default)Reviewing the listed bill and target organization combinations and flagging the ones to make common yourself.
Automatic Common BOM Upload TemplateMaking everything listed common: every row is downloaded with Create Common Bom set to Yes and already marked for upload. Clear the flag or delete the rows you do not want.

Step 1 – Set the parameters

Open BOM Common Bill of Materials Upload in Blitz Report, choose the template and set the parameters:

ParameterMeaning
Source Organization CodeThe master organization whose bills are made common.
Common BOM ScopeAll Organizations: every organization under the same master organization; Organization Hierarchy: the organizations below the source organization in the Target Hierarchy; Single Organization: the Target Organization only.
Target HierarchyThe organization hierarchy, when the scope is Organization Hierarchy.
Target OrganizationThe target organization, when the scope is Single Organization.
Enable Attributes UpdatePassed to Oracle’s common bill creation, as the Enable Attributes Update option of the Create Common Bill window: Yes lets the target organization change component attributes such as supply type, subinventory and locator on its common bill.
Assembly / Alternate BOMRestrict the download to one assembly, and to an alternate bill instead of the primary bill.
Show Sub-AssembliesYes also lists the bills of the sub-assemblies and substitute items in the bill structure as their own rows.
Show Missing BOMS onlyYes lists only combinations where the target organization does not have a bill for the assembly yet.
Auto Populate Upload ColumnsYes downloads every row with Create Common Bom set to Yes, ready to upload. The Automatic template sets it.
Implemented Only / Display / Effective DateWhich components count when the bill structure is exploded: implemented components only, and current, future or all components as of the effective date.
Blitz Report run screen for BOM Common Bill of Materials Upload with Source Organization Code V1, Common BOM Scope All Organizations and Assembly AT23808

Step 2 – Run to download the Excel file

Click Run. Blitz Report downloads and opens the Excel file with one row per bill and target organization. With scope All Organizations, organizations where the assembly item is not assigned are listed too, with Is Item Defined In Tgt set to No.

Excel file listing assembly AT23808 per target organization, with J1 and J2 showing the item defined and no missing components

Step 3 – Enter or change the data

Set Create Common Bom to Yes on the rows to make common (in the Automatic template it is already set; clear it where you do not want the row). Rows you do not flag are not processed. Before flagging a row, check the readiness columns:

  • Is Item Defined In Tgt – No means the assembly item is not assigned to the target organization, and the row will fail.
  • Is Bom Defined In Tgt – Yes means the target organization already has a bill for this assembly and alternate, and nothing is changed.
  • Is Common Bom In Tgt – Yes means the target organization already has a common bill referencing this source bill.
  • Comp Items Not Defined In Tgt – component and substitute items of the bill that are not assigned to the target organization. Assign them first, or the row fails.

A row with Is Item Defined In Tgt Yes and Comp Items Not Defined In Tgt blank can still be rejected by Oracle: the assembly and its components must also have compatible item attributes in the target organization, for example not be engineering items there, be BOM enabled and have a compatible item type.

The other columns identify the bill and cannot be changed. Do not add rows: only downloaded rows can be processed.

Create Common Bom set to Yes for target organizations J1 and J2, marking both rows for upload

Step 4 – Validate and Save

Click Validate and Save. This checks the rows for missing required values and saves the file.

After Validate and Save the flagged J1 and J2 rows show status Valid

Step 5 – Upload the file

In Blitz Report click Upload and select the saved file. This submits the upload request, which creates the common bill in the target organization for each flagged row, together with any sub-assembly and substitute-item bills of the structure that the target organization does not have yet. A row that fails is rolled back completely, including the sub-assembly bills created for it.

Oracle File Upload page with the saved Excel file selected for upload

Step 6 – Review the result report

When the request completes, a result report opens listing every row with its status and message. A successful row shows BOM Created (n), where n is the number of bills created for it, sub-assembly bills included. The readiness columns are evaluated again, so Is Bom Defined In Tgt and Is Common Bom In Tgt show Yes.

Result report showing both rows with status Success and message BOM Created (2), the assembly and its sub-assembly bill

What’s produced

  • Common bills of material in the target organizations that reference the source organization’s bills, including any sub-assembly and substitute-item bills that were missing.
  • A result report listing every row with its status and message.

Common questions

Does it copy the components into the target organization?
No. The target bill is a common bill that references the source bill, so component changes in the source organization apply to the target organization too.

Do I have to make the sub-assembly bills common first?
No. The upload walks the bill structure and makes every sub-assembly and substitute-item bill common in the target organization where it does not exist yet, starting from the lowest level.

Why is the downloaded file empty?
Only organizations under the source’s master organization that your responsibility can access are listed, and with Show Missing BOMS only set to Yes, combinations where the target already has a bill are left out. Check the responsibility’s organization access, or set Show Missing BOMS only to No.

Can I upload the same file again?
Yes. Bills that already exist in the target organization are reported as no action and left unchanged.

Troubleshooting

MessageCauseWhat to do
This API only supports Upload of existing BOMSThe row was not downloaded (for example a row added by hand).Download the bill and target organization combination and flag that row.
No action takenThe row was marked for upload with Create Common Bom blank, for example after clearing the flag in the Automatic template.None, or set Create Common Bom to Yes to process the row.
Item is not defined in the Target OrganizationThe assembly item is not assigned to the target organization.Assign the item to the target organization and upload the row again.
No Action. Bom already ExistsThe target organization already has a bill for this assembly and alternate.None.
Following Component Items are not assigned in the Target Organization: …Components of the bill structure are not assigned to the target organization.Assign the listed items to the target organization and upload the row again.
Following Substitute Items are not assigned in the Target Organization: …Substitute items of the bill structure are not assigned to the target organization.Assign the listed items to the target organization and upload the row again.
(assembly) 1:One or more components of (assembly) in organization (source) have different properties in organization (target), or a component does not exist in the destination organization.A component cannot be used on the bill in the target organization, for example it is an engineering item, not BOM enabled or of an incompatible item type there.Correct the component’s item attributes in the target organization, or leave the row unflagged.
(assembly) 1:Manufacturing bill cannot be created for egineering item.The assembly item is an engineering item in the target organization, while the source bill is a manufacturing bill.Make the item a manufacturing item in the target organization, or leave the row unflagged.
(assembly) 1: … further messagesOracle’s bill of material api rejected the common bill for that assembly.Correct the cause named in the message, for example in the item or bill setup of the target organization.

SQL 270 lines

Parameters 13