The Consumption import allows you to mass import information about which activities consume items (parts).
Two options exist for the Consumption import: Add New or Merge.
•Selecting Add New will overwrite any existing items mapped to the selected activities. The only items that will be mapped to those activities are those included in the import file.
•Choosing Merge will add to or update current item mapping. The items in the import file will be added to the current item mapping; if the activity already has an item mapped to it and that item is not included in the import file, the mapping of that resource will not be affected by the import.
There are certain fields that must appear in the spreadsheet file used to import items. The table below lists the standard fields provided in Assembly Planner that are relevant to this import type. Each of these fields needs to be a column heading in the import spreadsheet file. The fields described as not mandatory do not need to be included as columns in the sheet.
In addition to the standard fields, the import file must also have a column that matches each user-created consumption custom field to be imported.
Consumption Standard Fields
Field |
Description |
Mandatory to Import |
OperationSeqNo |
The Operation Sequence Number (OpSeqNo) of the operation to which the consumption mapping applies. |
YES |
OperationEffectiveFromDate |
The Effective From Date of the operation. It is not mandatory to make an entry in this column, it is optional. May be useful in cases where there are multiple operations with the same OpSeqNo that have different effectivity dates. |
YES |
OperationEffectiveToDate |
The Effective To Date of the operation. It is not mandatory to make an entry in this column, it is optional. May be useful in cases where there are multiple operations with the same OpSeqNo that have different effectivity dates. |
YES |
ActivitySeqNo |
The Activity Sequence Number (ActSeqNo) of the activity (under the specified OpSeqNo) to which the consumption mapping applies. Either the ActSeqNo or the ActivityID is required. |
YES* |
ActivityID |
The Activity ID of the activity (under the specified OpSeqNo) to which the consumption mapping applies. Either the ActSeqNo or the ActivityID is required. |
YES* |
ActivityEffectiveFromDate |
The Effective From Date of the activity. It is not mandatory to make an entry in this column. Mandatory if using ActSeqNo. |
YES |
ActivityEffectiveToDate |
The Effective To Date of the activity. It is not mandatory to make an entry in this column. Mandatory if using ActSeqNo. |
YES |
ItemID |
The ID of the item (part) that is consumed. The import will work even if the item ID does not exist in the database; it is up to the user to ensure that valid items are mapped to the activities. |
YES |
ItemRevision |
The revision of the item specified. The revision rules section explains what revisions are supported. If no revision is specified, Assembly Planner will use the current revision of the item. |
NO |
OpSeqNo |
This is the OpSeqNo stored in the BOM, if applicable. Some clients store an OpSeqNo in the Bill of Materials, which is then matched to the OpSeqNo of the operation to build consumption (e.g. with the AutoBuild feature). |
NO |
ParentID |
Specifying a Parent ID for the item allows consumption to be added from the BOM. This may be import if you are also using the Automatic Model-Option Mapping tool. |
NO |
ParentRevision |
The revision of the parent item specified. The revision rules section explains what revisions are supported. If no revision is specified, Assembly Planner will use the current revision of the item. |
NO |
Quantity |
The quantity of the item consumed by the process. |
NO |
Units |
The units in which the item is consumed (EA, PC, IN, FT, OZ, etc). |
NO |
RoutingID |
The process is added to the Routing that is specified in RoutingID. |
YES |
RoutingType |
Users typically create routings with a Routing Type of ‘M’. However, other values (such as A) will be valid as well. The list of available Routing Types may have to be configured for different clients. |
YES |
PlantID |
The process is added to the plant whose ID is specified. Many users only have one plant set up in their Assembly Planner system; if you are unsure as to the ID, check in the Library > Plant Tab. |
YES |
*Either the ActSeqNo OR the ActivityID is required for the import. You only need one of the two, but you are allowed to use both.
Example Consumption Import Spreadsheet
*Note - Red Headers have to be filled in for import to work correctly.