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 (MATMAS material master), BAPI-style CSV/Excel exports with SAP field-name headers |
| Oracle WMS Cloud | CSV item 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 |
LOP's SAP import has been validated against real SAP system exports (SAP IDES and integration-project samples) covering the structures described below.
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
For generic CSV and Excel exports (not SAP or Oracle — see below), LOP applies AI Smart Detection automatically when it's useful. You don't turn anything on: LOP analyzes every file's structure instantly (header row, footer rows, decimal separator, merged cells, combined-dimension columns), and if the column mapping is uncertain — unfamiliar headers, or a required field it couldn't map — the AI reads your headers and sample data and fills in the mapping for you to review. On a file it already recognizes with confidence, it doesn't run. An "Improve with AI" button on the mapping step lets you trigger it on demand if the automatic mapping looks off.
SAP and Oracle files never go through the AI. Fixed-format exports are mapped exactly from their known field codes (see the SAP and Oracle sections below), by design — so a canonical field like MATNR or BRGEW is never mis-guessed. AI Smart Detection applies only to the generic CSV/Excel path.
For a detailed guide — including the import verification checks, the AI review loop, mapping profiles, and combined-dimension cells — 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, and German directly, so exports from regional SAP implementations or locally-configured WMS instances are handled without any configuration changes. Headers in other languages — French, Spanish, Italian, Dutch, Polish, and more — are handled by AI Smart Detection on the generic CSV/Excel path.
Examples of directly-recognized header synonyms:
| Property | English | Turkish | German |
|---|---|---|---|
| Item name | Name, Description, Material | Malzeme Adı, Açıklama | Bezeichnung, Materialname |
| Length | Length, L | Uzunluk, Boy | Länge |
| Weight | Weight, Gross Weight | Ağırlık, Brüt Ağırlık | Gewicht, Bruttogewicht |
| Quantity | Quantity, Qty | Miktar, Adet | Menge, Anzahl |
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. For SAP files that carry a unit code (MEABM for dimensions, GEWEI for weight), LOP fills these in automatically; otherwise set them here. Oracle WMS Cloud typically uses 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 are supported for the MATMAS material-master family — root elements MATMAS01 through MATMAS05, both plain and namespaced. LOP reads material data from the E1MARAM segment and descriptions from the nested E1MAKTM/E1MAKTG segments, including the versioned external segment names (E2MARAM… / E2MAKTM…) that some ports and middleware emit. Custom extension (Z-) segments are tolerated and ignored, so a customer-extended IDoc still imports cleanly.
For each material LOP reads the material number (MATNR — SAP's leading zero-padding is stripped for readability), the dimensions (LAENG, BREIT, HOEHE), and the weight. Gross weight (BRGEW) is used for load planning, with net weight (NTGEW) as a fallback — packaging weight counts against payload and axle limits.
Item names come from the material description (MAKTX). When a description exists in several languages, LOP prefers English, then Turkish, then the first available.
Unit codes are authoritative. When the file carries a dimension unit (MEABM) or weight unit (GEWEI) — SAP/ISO codes such as MM/MMT, CM/CMT, M/MTR, KG/KGM, G/GRM — LOP uses it directly instead of guessing from value magnitudes. BAPI-style CSV/Excel exports that include these unit columns are read the same way.
BAPI / table exports are supported as CSV or Excel files whose headers use the SAP field names (MATNR, MAKTX, LAENG, BREIT, HOEHE, BRGEW, NTGEW, MEABM, GEWEI, …). LOP auto-detects the delimiter and maps these headers to item properties.
Flat-file (fixed-width) IDoc is not supported. If your SAP system produces a flat-file IDoc — a fixed-width text file that begins with an EDI_DC control record — re-export it as IDoc XML instead. LOP detects the flat-file format and asks you to do exactly this, rather than importing it incorrectly.
Oracle WMS Cloud Notes
Oracle WMS Cloud CSV exports use a fixed column structure from the Outbound Order Management module. LOP recognizes the common Oracle column headers including ITEM / ITEM_NUMBER, DESCRIPTION / ITEM_DESCRIPTION, ITEM_LENGTH / ITEM_WIDTH / ITEM_HEIGHT, UNIT_WEIGHT / ITEM_WEIGHT, the unit-of-measure columns (UOM / STANDARD_UOM / WEIGHT_UOM), and the quantity (QTY / ORDERED_QTY).
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 profile. Saved profiles are shared across your organization.
To save a profile:
- Complete the mapping and reach the preview step in the wizard.
- Click Save profile and give it a descriptive name (for example, "SAP Weekly Outbound Export").
On future imports, LOP recognizes the same template automatically — regardless of column order or accented characters — and offers to apply the saved profile in one click. Applying it is instant and uses no AI. Saving again on a recognized template updates the existing profile rather than creating a duplicate. See Mapping Profiles for details.
Import profiles are especially useful when combined with Templates. A template defines the container configuration and item types for a recurring shipment type, while a mapping profile handles the column mapping for that shipment's cargo list. Together they turn a recurring load-planning task into a few clicks.