Skip to content

Bulk costing required attributes

If you provide a scenario name that exists in the database when you initialize bulk costing, aPriori populates the inputs with everything that currently exists for that scenario.

  • If you have User Defined Attribute values for “Part1-scenario1”, and you start a bulk costing that includes “Part1” and “scenario1” in the New Bulk Cost Group dialog box, then the existing UDA values are used. Since they exist, they are used no matter what Processing Input Rule you have selected..
  • If you change the scenario name in the bulk costing UI, then aPriori does not load that data from the database, and whatever values you provide in the bulk costing UI is used again, regardless of what Processing Input Rule you have selected.
  • If you create a new bulk cost group with scenario name “scenario0” and then in the bulk cost UI you change the scenario name to “scenario1”, it doesn’t matter that Part1 already has UDA values in aPriori; the bulk costing UI is not filled out with UDA values.

In summary, you can enter values for UDAs when bulk costing, and must provide values for required attributes. If you are bulk cost existing components and want to use existing required attribute values, you must do one of the following:

  • Collect all scenarios into a container assembly, roll-up, or dynamic roll-up and use Deep Costing. The existing UDA values are pulled in for all scenarios.
  • If all scenarios have the same scenario name, ensure that that scenario is used when creating the new bulk cost group. All existing UDA values will be pulled into the bulk costing UI.