ERP/WMS Import
For organizations that manage cargo data in enterprise resource planning (ERP) or warehouse management systems (WMS), LOP can import item lists directly from the file formats these systems produce. This eliminates manual re-entry and reduces the risk of transcription errors.
Supported Systems and Formats
| System | Supported Export Formats |
|---|---|
| SAP ERP / SAP S/4HANA | IDoc XML, BAPI flat file exports |
| Oracle WMS Cloud | CSV exports from warehouse order management |
| Generic ERP / WMS | Standard CSV and Excel with auto-detected columns |
| Custom systems | CSV or Excel exports with manual column mapping |
If your ERP system is not listed above, use the generic CSV/Excel import path. Most ERP systems can export to a standard spreadsheet format. See Importing from Excel or CSV for instructions.
Smart Format Detection
When you upload a file in the ERP import dialog, LOP analyzes its structure before asking you to configure anything. The detection engine examines:
- File format and encoding
- Column header names and patterns
- Data field formats (date stamps, numeric codes, SAP material numbers)
- XML schema and IDoc segment structure (for SAP IDoc files)
LOP assigns a confidence score to each detected format and presents the most likely match. In most cases you can proceed directly to the preview step without making any adjustments.
Format detection is most reliable when your export file includes a header row with original system column names. Avoid stripping headers before uploading.
AI Smart Detection
When you enable AI Smart Detection (checkbox in the import dialog), LOP uses a two-stage analysis pipeline to understand your file automatically:
Stage 1 — Structural Analysis runs instantly and detects:
- The header row location (even if it is not row 1)
- Merged header cells (automatically expanded)
- Footer rows and summary totals (excluded from import)
- Decimal separator format (European comma or US period)
- Combined dimension columns (e.g., "1200x800x600" or "4 x 2.4 x 2.3")
Stage 2 — AI Enhancement uses AI to map your columns to item properties with confidence scores:
- Green badge (≥90%) — high confidence, ready to use
- Amber badge (70–89%) — medium confidence, verify the mapping
- Red badge (under 70%) — low confidence, review and correct manually
The AI also detects dimension and weight units from your column headers. You will see labels like "AI detected: meters" next to the unit dropdown. If units are inferred from value magnitudes instead of headers, an amber "Inferred from values — verify" label appears.
The more standard your column header names are, the higher the AI confidence will be. Headers like "Length (mm)" or "Gewicht (kg)" produce near-perfect detection. Cryptic codes like "F3" or "COL_A" may need manual correction.
For a detailed guide on how AI Smart Detection works, see the dedicated AI Smart Detection page.
Import to Library
The import dialog works for both adding items to a plan and importing directly to the Item Library. When you open the import dialog from the Item Library page (instead of from a plan's editor), items are saved as reusable library items rather than plan-specific items.
Multi-Language Column Recognition
LOP recognizes column header names in English, Turkish, German, and French. This means exports from regional SAP implementations or locally-configured WMS instances are handled without any configuration changes.
Examples of recognized header synonyms:
| Property | English | Turkish | German |
|---|---|---|---|
| Item name | Name, Description, Material | Malzeme Adı, Açıklama | Bezeichnung, Materialname |
| Length | Length, L | Uzunluk | Länge |
| Weight | Weight, Gross Weight | Ağırlık, Brüt Ağırlık | Gewicht, Bruttogewicht |
| Quantity | Quantity, Qty | Miktar | Menge |
Import Wizard
The ERP import follows the same step-by-step wizard as the standard spreadsheet import, with ERP-specific additions at the format detection step.
Step 1: Upload your export file Open the Items Panel, click Import, then select ERP / WMS Import. Upload the file exported from your system.
Step 2: Confirm format detection LOP displays the detected format and confidence level. If the detection is incorrect, select the correct format manually from the dropdown.
Step 3: Review column mapping For CSV and Excel exports, review the auto-generated column mapping and adjust any fields that were not detected correctly. For SAP IDoc XML files, LOP maps segments automatically — no manual mapping is required.
Step 4: Set units Confirm the dimension and weight units used in your export. SAP typically exports in millimeters and kilograms; Oracle WMS Cloud may use centimeters. Check your system's export configuration if you are unsure.
Step 5: Preview items Review the first several rows of parsed items before committing the import. Confirm that dimensions and weights look correct.
Step 6: Import Click Import Items to add all items to the plan.
SAP-Specific Notes
IDoc XML exports from SAP contain dimensional data in the E1MARAM or material master segments. LOP reads the gross weight (BRGEW), volume (VOLUM), and dimensions (LAENG, BREIT, HOEHE) fields automatically.
BAPI flat file exports typically contain tab- or pipe-delimited text. LOP detects the delimiter automatically and maps the standard SAP field names.
SAP material master records store dimensions and weights in the units of measure configured for each material (stored in GEWEI and VOLEH). LOP reads these unit fields and converts accordingly. If your SAP configuration uses non-standard units of measure, verify the preview step carefully before importing.
Oracle WMS Cloud Notes
Oracle WMS Cloud CSV exports use a fixed column structure from the Outbound Order Management module. LOP recognizes the standard Oracle column headers including ITEM_NUMBER, DESCRIPTION, UNIT_WEIGHT, UNIT_LENGTH, UNIT_WIDTH, UNIT_HEIGHT, and QTY_ORDERED.
Saving Import Profiles
If you import from the same system regularly — for example, a weekly shipment export from your SAP instance — you can save the column mapping as a named import profile. Saved profiles are available to all users in your organization.
To save a profile:
- Complete the column mapping step in the wizard.
- Click Save as Profile and give it a descriptive name (for example, "SAP Weekly Outbound Export").
- On future imports, select the saved profile at the format detection step to skip manual mapping entirely.
Import profiles are especially useful when combined with Templates. A template defines the container configuration and item types for a recurring shipment type, while an import profile handles the column mapping for that shipment's cargo list. Together they can reduce a recurring load planning task from 30 minutes to under 5 minutes.