ERPNext to EDGEBIC: The Data Mapping Reference

ERPNext data export scheduling comes down to five saved report exports: Item, Workstation, BOM operations, Work Order and optionally Job Card hours, mapped once into EDGEBIC import masks and re-run each cycle. In EDGEBIC by User Solutions the integration is entirely file-based, using xlsx or csv exported from ERPNext and loaded through a saved mask, so there is no connector to install and nothing in ERPNext to modify.

What to export, and in what order

Imports have dependencies, so the order is not optional. Work centers and items must exist before a routing can reference them.

Those are the only entity types the masks accept, so anything else in ERPNext stays in ERPNext. Notably there is no mask for departments, machine pools, or operators and skills: those are configured in EDGEBIC directly. The sequence-dependent setup matrix is configured per work center too, though its editor carries its own Import and Export CSV.

1. Item to Product

Export finished items and any sub-assemblies that have their own routing. Raw materials only need to come across if you want their unit cost to feed material cost in a quote.

2. Workstation to Workcenter

Two of these have no ERPNext source and are worth deciding by hand at mapping time. Number_Of_Instances matters most: an ERPNext workstation usually represents one machine, but if yours stands for a bank of three identical machines, say three here or the schedule will plan a third of your real capacity. Is_Bottleneck and One_Per_Day_Flag likewise come from what you know about the plant, and they are settable through this mask, which is the easiest route for both.

3. BOM operations to BOR

This is the export that repays care. Put every operation for one finished item in a single file, because a re-import replaces that item's entire routing per run.

ERPNext BOM Operation rows give you the workstation, the operation name and the operation time, which is most of what a routing step needs. The auto-chaining option is worth leaving on: it links steps in sequence order so you never maintain a next-step column, which is the field most likely to drift.

If your BOM records a single operation time that includes setup, split it deliberately rather than letting it all land as run time, since run time scales with order quantity and setup does not. Handling combined setup and run time from your ERP covers the split.

4. Work Order to SalesOrder

Map the job date and the due date to different sources deliberately. The due date is what lateness is measured against; the job date is when work may start. Mask options can derive one from the other when only one is present, so decide rather than let it be inferred. Importing customer due dates vs internal need dates is the fuller argument.

Keeping Job_Number aligned with the ERPNext Work Order name pays for itself the first time someone has to reconcile the two systems.

5. Job Card or Timesheet to Actuals

Optional, and only useful once jobs are scheduled in EDGEBIC.

Mask options let you derive hours from pieces or the reverse, mark operations complete on import, and accept that earlier steps have no actuals yet. Rows fail when the job number or work center does not match a scheduled operation, which is almost always a spelling difference rather than a missing record.

Conversions and upsert rules

Time units. ERPNext operation times are in minutes. EDGEBIC schedules in hours, so set the column's conversion factor to 0.016667 for minutes and leave it empty for hours. Seconds use 0.000278. This is the most common ERPNext mapping error, and it announces itself: times land sixty times too large.

Updates. By default a row that matches an existing record is counted as reused and left alone. If your cycle is meant to refresh existing data, turn on the update option, or nothing will change on the second run.

Auto-create. Products, customers and work centers named in a file but not yet present can be created on the fly, which is convenient during a first load and worth reviewing afterward so a typo does not quietly become a new work center.

Matching. Every import matches on a natural business key and is not case-sensitive, so WIDGET-A finds Widget-A.

After the import

Imports change data and never produce a plan, so run the scheduler afterward. Then check load before dates: a machine showing impossible hours usually means an instance count or a time conversion is wrong, and both are visible in load long before they are visible in a delivery date.

Set the cycle up as a routine rather than a project, per keeping ERP and EDGEBIC in sync. When you need the plan outside EDGEBIC, export the schedule grid as a snapshot, which is a share-and-analyze artifact rather than a file that loads back.

The takeaway

ERPNext data export scheduling means five saved exports mapped once: Item to Product, Workstation to Workcenter, BOM operations to BOR with every operation for one item in a single file, Work Order to SalesOrder with the job and due dates mapped deliberately, and optionally Job Card hours to Actuals. Set the minutes conversion factor, decide instance counts and the bottleneck flag by hand, turn on updates for recurring runs, and always schedule after importing. See the platform on the EDGEBIC overview, the upgrade path on the RMDB to EDGEBIC guide, and pair this with which ERP fields EDGEBIC needs to schedule and why EDGEBIC connects to every ERP the same way.