Loading a BOM

Tip: See Walk-through: updating Quoted Total Cost using BOM Loader for a full example of use.

  1. Create and populate a .csv file that lists the components that are to be BOM Loaded. See CSV File for BOMs.

  2. From the Digital Factory Toolset window, click BOM Loader:

  3. Click OpenIcon next to the Import button:

  4. In the Open window, select the CSV file that contains the BOM you want to import, then click Open.

    Note: The CSV file must be formatted correctly - see Formatting a BOM.

    Tip: This window opens automatically when you first open the BOM Loader.

  5. Once you select the .csv file, the window updates to display the Column Mapping pane:

     

    1. Rollup Name (optional): to import into a roll-up, enter a new roll-up name in the Rollup Name field, or click the “...” button to use an existing roll-up.

    2. Functional Template (optional): click OpenIcon , and open your functional group template (see Functional groups).

    3. Default Scenario Name: enter a descriptive string, appended to the name of any parts and also to any roll-up (if specified).

      Note: If a specific scenario name field is NOT present in the BOM file for a particular row, then this default name is used instead. If a specific scenario name IS specified in the BOM, then it will be used. aPriori resolves any conflicts with existing names by appending (2), (3), etc.

    4. Processing Rule if Scenario Exists: select one of the following options:

      1. Update: Update the existing scenario with the values imported from the BOM.

      2. Skip: Do not update the existing scenario.

      3. Create New Scenario: Make a copy of the existing scenario, then update the copy with values that are in the BOM load CSV file.

  6. In the Column Mapping pane, select your mapping, to pull the column names from the .csv file, and allow you to associate these with a particular aPriori field. You can either:

    • Select an existing mapping:

    • Create a new mapping:

  7. Select the fields from the drop-down menu that map with the .csv columns

    When mapping:

    • You must map the Part Number, Quantity, and Level fields, and any required User Defined Attribute (UDA) fields if present.
    • You must also set the field Type if you are loading in components with non-integer quantities or loading in component placeholders for assemblies (such as single components that will be assemblies when the product is designed). Valid values for this field include Part, Assembly, or Bulk Item.
    • Single components can be designated as assemblies in a BOM load. Additionally, BulkItem is used to designate non-integer components like fluids. The quantity field in aPriori does not accept non integers. When a component is specified as a BulkItem, the quantity from the BOM file is appended to the description field and the quantity in aPriori is set to 1.
    • To map a field, click the aPriori Field cell and select the field you want to map to from the drop-down list. By default, manually costed parts are not totaled. If you wish to have these values aggregated, click the checkbox labeled Calculate aggregate costs for Manually Costed components? When enabled, the following fields are computed during load unless they are mapped from a value in the CSV file: other direct costs, variable costs, amortized investment, fully burdened cost, aggregate fully burdened cost, capital investment.

  8. To specify a different currency for manually costed components only, use the drop-down menu labeled Manually Costed Currency. aPriori-costed components will use the currency from the Digital Factory.

  9. Change the Unit System if required.

  10. By default, manually costed parts are not totaled. To aggregate these values, click the checkbox Calculate aggregate costs for Manually Costed components?

  11. Save the mapping by clicking on the Save button or going to File > Save Changes.

  12. Click Import to import the information from the CSV file into aPriori

  13. A new window shows the import results: