Importing parts

Owned by Benoît Wambergue
Last updated: May 07, 2024
3 min read

Parts are a very important asset in the ERP, possibly the most important one. They drive the behaviour of the entire system, from stock strategies to price breaks.

Before trying to bulk import data, make sure you have a good understanding of the impacts of each information of the part record. We strongly recommend you read the dedicated page of the user manual and practice over a few examples before you start importing sample data and finally bulk import the entire dataset.

https://forterro-fwe.atlassian.net/wiki/spaces/FOR/pages/31948848

Minimalist import

The smallest set of information you need to import products onto the system is the description. Everything else can be defaulted or automatically generated for the part number. In this case, all you need is a csv file displaying two columns: a section header, and the description column.

Although possible, this will however limit your ability to edit in bulk, as the system will require a stronger identification of the product when updating the records. Which information can either be the part number (code), or the EDI identifier.

part,description

Full CSV with section break

The following template document will allow you to bulk import parts, and their associated revisions, characteristics and foreign descriptions. It is split in sections, each one starting with the name of the section which you will need to repeat on each line of the file. It is comma separated so make sure you are not using commas in your comments and texts.

The mandatory information are identified by an asterisk (*).

part,Part number *,Description *,Type (1:Material 2:Tool 3:Part 4:Kit 5:Phantom 6:Customer Service),Source (1:Purchased 2:Produced),Status (0:Not valid 1:Valid),Stock UOM code *,Unit weight (kilogram),Unit volume (cubic metre),Question scenario code,Formula scenario code,Drawing number,Last revision,Created date [dd/MM/yyyy],EDI Id,General comment,Purchase UOM code,Conversion rate Stock/Purchase UOM,Product group code,FAI Status (no;yes),Type of kit (0:Sales kit 1:Efficiency kit), revision,Revision code,Applicability date of revision [ddMMyyyy],Revision name, characteristic,Alphanumerical value,Date value [ddMMyyyy],Numerical value,Characteristic code, description,Description in language,Language code, sales,Public price,New public price,Applicability date of new price [dd/MM/yyyy],Tariff family code ,Warranty duration in months, procurement,Procurement strategy (1:To stock 2:To order 3:To project) *,Management type (1:MRP 2:Order point 3:Not managed 4:Stocks managed) - 4 not available for strategy 1 - 1 and 2 not available for strategies 2 and 3 *,Batch policy (1:Economic quantity 2:Batch by batch) *,Serial numbering (no; yes),Quality control scenario code,Code of main store of entry,Code of main store of withdrawal,Consumption method (blank:no choice 1:pre-consume or declare 2:post-consume or backflush),Last purchase price,Code of main supplier,Lead time,Buffer over lead time,Economic quantity or minimum batch size,Multiplier on over economic quantity,Security stock threshold,Reorder point quantity,Maximal stock level,Workload per unit,GENCOD,MRP grouping label,Code of Sales and Operations Plan parent product,Code of batch counter,Code of serial number counter, finance,VAT type label (default values: Standard - Reduced - Zero-rated) *,Valuation method (1:Last purchase price 2:WAC 3: Planned full cost or landed cost 4: Standard price of fixed cost) *,Purchase nominal code,Sales nominal code,Price expressed for quantity,WAC,Standard price,Planned full cost,Accounting classification (0: Raw material 1:Merchandise 2:Services 3:Manufactured products 4:Misc),Code of country of origine,

Â