Upload Orders Through the ERP Planner
Import spreadsheet-based orders, map columns, resolve machine values, preview the result, and commit the upload.
Goal
Bring external order data into the platform in a controlled, preview-first flow.
Before You Begin
- Required access: Admin or Page Access
erp_uploads. - Entry points:
/erp-uploads
Begin on the ERP Upload Planner page.
Preconditions
- The upload file is ready.
- You know which spreadsheet columns represent orders, products, dates, and machines, and which time convention the file uses.
- You can review the existing production plan if the file proposes changes to scheduled operations.
Steps
Upload the spreadsheet file
Select your order file. Check its file name, row and column count, and sample contents to confirm you selected the right data.
Correct source values if needed
Select Expand to edit to correct individual values or paste matching groups of values from Excel. Review the changed-cell count and save your corrections; the preview highlights saved changes. Column headings and row counts cannot be changed here. Closing without saving discards unsaved corrections and leaves the original file unchanged.
Map columns and machine references
Map the source columns to platform fields, including order tags where needed. Reuse a saved mapping if it matches this file. Match external machine names or codes to the correct machines.
Check import scope and time interpretation
If needed, limit the import to orders that already have a machine assignment. Choose standard or industrial-minute interpretation to match the file's time convention. Review the explanations of changes to preparation and production times and the affected rows.
Review the preview and proposed changes
Run the preview and review schedule warnings. Open What this import will change to compare counts of new, updated, and existing orders, products, customers, operations, and assignments. Expand the row-by-row details to check schedule changes, new operations and assignments, and recalculated durations. Correct the file or mapping if the proposals do not match your intent.
Review scheduling conflicts
For each conflict grouped under an order, read the reason and choose Move to [new target] to apply the file's assignment, Keep on [current target] to retain the existing assignment, or Keep both for parallel work at both targets. If the review flags a conflict for manual resolution, use the Assignment Planner.
Confirm the import
Confirm once you have reviewed the proposed changes and conflict decisions. Follow the upload progress.
Check the applied results
Read the outcome summary to see which decisions were applied. If a decision could not be applied, review its explanation and check the affected operation in the Assignment Planner. Production may have started after you reviewed the conflict.
Confirm the Four Import Stages
Upload File → Map Columns → Assign Machines → Review & Save uses CSV, XLS, or XLSX. Map Order Number, Product, Planned Start, Planned End. Choose ALL Units / 1 Unit, ordinary/industrial minutes, commit scope, and the initial priorities for new records with empty priority cells. Initial operation priority defaults to 100. Save Mapping is per user; manual machine/hall-pool assignment overrides mapping, and Reset restores it.
Run Check as a dry run. NEW / NEU, CHG / GEÄ, and IMPACT show creation, update, and affected planning calculations. Check saves nothing. If data changes, run Check again before Save.
Rows without scheduling or with start after end are not processed. Re-import matches product, order, work-order product, operation sequence, and machine assignment. Empty update cells preserve values; existing priorities, protected fields, and production history are unchanged. Missing file rows do not delete records. Operations with recorded work cannot move; ambiguous multiple-target conflicts need manual planner review.
Example: If an imported planned time of 100 minutes covers 50 units, choose ALL Units. If it is 2 minutes per unit, choose 1 Unit. Choosing the wrong option changes the planned duration.
Decision Points
- Whether to reuse saved mappings or adjust them for the current file.
- Whether the preview is clean enough to commit or needs correction first.
- Whether to move an existing assignment, keep its current target, or retain both targets for parallel work.
Expected Result
The upload creates, updates, or reuses platform records according to the reviewed mapping. The outcome summary confirms which conflict decisions were applied and identifies decisions that could not be applied.
Common Problems and Edge Cases
- Missing required columns will block a useful preview.
- Machine names from the source file may need manual mapping before commit.
- Users may need to re-upload after correcting spreadsheet structure or data format issues.
- If preparation or production times look wrong, check the affected row and the standard or industrial-minute interpretation before confirming.
- A conflict may require manual resolution, or its decision may no longer be applicable because production changed after review. Follow the explanation and inspect the affected operation in the Assignment Planner.