Importing & API Integration

planeus gives you flexible ways to bring data in from your current system landscape this makes it easier to connect planeus with erp, inventory, and scm systems without changing your core setup at minimum, planeus can import the following types of data order items (typically include customer orders, production orders or work orders) articles and technologies (typically include product data, routings, and boms) customers materials how data gets into planeus planeus supports two import methods manual and automated import manual import you upload an excel or csv file into planeus yourself this option works well when you want a simple file based exchange you import data only from time to time you want to test your mapping before you automate anything automated import planeus imports data on a regular schedule without manual work the system can import data from excel files csv files a database this option works well when you want planeus to stay aligned with your erp, inventory, or scm system on an ongoing basis license you would need the required license depends on the integration method you choose import for manual file imports automatic import for scheduled imports from files or databases api for integrations through the rest api optional licenses some use cases need additional licenses assemblies if you work with product structures or bom data parallel resources if planeus should plan multiple resources at the same time import settings go to administration → settings there you can configure the following changed delivery dates trigger rescheduling this applies to manual import, automatic import, and import through the weclapp interface email notifications for import errors this applies to automatic import and import through the weclapp interface for the weclapp integration , email notifications need a separate setup contact planeus customer service for more details what happens when source data changes? in the standard import process, if planeus imports data for a record that already exists, it updates that record instead of creating a new one so when something changes in its source data, planeus will simply updates existing record it will not create extra copies just because the source data changed this helps you keep planning data current without creating unnecessary duplicates or extra cleanup work user can see exactly what's changed every time new data is updated through importing, such as an master data item (e g , an article) or a planning object (e g , a project or an order item)