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 | No | 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 |
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 |