Data Structure for Importing

the data structure documented here shows the standard format in planeus important note for importing depending on how your import is configured, your actual data structure may differ you can always find the exact structure for your system in its excel template, which you can download during the manual import process importing articles the following fields define the standard import structure for articles and its routings (technologies) bold column names are required fields column description required data type note / validation articlenumber article number created automatically if it does not yet exist text articlename article name required if the item number does not already exist text articlegroupname article group no text amountunit unit of measurement no text created automatically if it does not yet exist location location no text parentarticlenumber article number of the parent structure level no text amount quantity required together with parentarticlenumber number templatename technology name no text templatenumber technology number required together with work step name text templateitemnumber work step number required together with work step name number defines the sequence of work steps templateitemname work step name no text created automatically if it does not yet exist lotsize lot size no number duration duration in seconds required together with work step name number together with setuptime, the total must be greater than 0 setuptime setup time in seconds required together with work step name number buffertime buffer time in seconds no number overlap overlap in percent no number templateitemdescription work step description no text resourcegroupname resource group required together with work step name text created automatically if it does not yet exist resourcename resource no text created automatically if it does not yet exist templateitemparentnumber parallel operation no number refers to the leading work step number pool pool required together with requiredpoolcapacity text requiredpoolcapacity pool capacity usage no decimal number important note for technologies the work step name decides whether planeus should import a technology together with the item if you provide a work step name, you also need to fill these fields templateitemnumber duration setuptime resourcegroupname these fields stay optional overlap templateitemdescription resourcename pass duration, setuptime, and buffertime in seconds what planeus detects automatically for item imports planeus automatically detects new and changed items new, changed, and deleted technologies new, changed, and deleted work steps importing order items (production orders) planeus automatically detects new and changed projects new and changed order items new customers planeus reschedules order items when any of these values change item item quantity scheduling direction delivery date bold column names are required fields column description required data type notes / validation projectnumber project number required if projectname is not provided text projectposition order item number yes number projectname project name required if projectnumber is not provided text customernumber customer number required if customername is not provided text created automatically if it does not yet exist customername customer name required if customernumber is not provided text created automatically if it does not yet exist articlenumber item number yes text articlename item name no text articleamount item quantity yes decimal number must be greater than 0 articleamountunit unit of measurement yes text created automatically if it does not yet exist deliverydate delivery date yes date also called terminationdate; start point for backward scheduling handoverdate handover date no date start point for forward scheduling termination forward / backward scheduling yes text orderdate order date no date confirmed confirmed no text allowed values yes / no orderresponsible responsible person no text first name and last name in any order, separated by spaces comment comment no text importing customer data the following fields define the standard import structure for customer master data bold column names are required fields column description required data type customername customer name yes text customernumber customer number yes text street delivery address street no text zipcode delivery address postal code no text city delivery address city no text country delivery address country no text email delivery address email address no text phonenumber delivery address phone number no text contactpersonfirstname delivery address contact person first name no text contactpersonlastname delivery address contact person last name no text importing material data bold column names are required fields column description required data type materialnumber material number yes text materialdescription material description yes text amountunit unit of measurement yes text