Aggregated Parts and Adding Usage

Purpose

It is not uncommon for a given product or order to contain multiple instances of the same part used. For example, an electric box sign may use sheet aluminum for the top, sides, bottom and back. All of these may be represented as separate parts on the same product. Similarly, the labor applied for fabricating the aluminum may be included as separate parts. This separation is useful for the computation of costs, but can be cumbersome for production when they have to select between the different parts to apply labor and material usage.

To improve the interface for the production user, the Control parts grid includes summary views which aggregate similar parts into one logical part. Part usage may be applied to the aggregate part and the usage automatically distributed between the composite parts.

Parts Grid in Order Entry

The parts grid in order entry has four summary views:

  • Detail View
    The detail view does not summarize the parts. So there is one part per line.
  • Order Summary View
    The order summary view consolidates all part which share the following:
    • Part
    • Production Warehouse
    • Is Replenishing Part
  • Top-Level Item Summary View
    The top-level item summary view consolidates all part which share the following:
    • Top Level Line Item
    • Part
    • Production Warehouse
    • Is Replenishing Part
  • Line Item Summary View
    The line item summary view consolidates all part which share the following:
    • Line Item
    • Part
    • Production Warehouse
    • Is Replenishing Part

Posting Usage on the Parts Grid in a Summary View

When posting actual usage to an aggregated part, the usage is distributed among the individual parts according to a specified logic.

The details of what logic is used to distribute the usage among aggregate parts can be found here.

See Also