Syteline to EDGEBIC: The Data Mapping Reference

Mapping Syteline data into EDGEBIC is a column-mapping exercise rather than a development project: you export items, resources, current routings, open job orders, and optionally labor transactions to Excel or CSV, then drag each source column heading onto the matching EDGEBIC field once and save it as a reusable import mask. This reference lists what maps to what, which columns are mandatory, how unit conversion and blank cells behave, and what every row outcome means when a run finishes.

EDGEBIC by User Solutions integrates with Syteline (Infor CloudSuite Industrial) through those masks rather than a certified connector, so nothing is installed inside the ERP and nothing enters its upgrade path. If you have not read the end-to-end version, start with the complete Syteline integration guide. This post is the lookup table you keep open while building masks.

The load order

Import in dependency order. Later files reference records that earlier files created.

Two entity types have no Syteline origin and are built from a spreadsheet you write yourself: Shift (one row per shift with a start and end pair per weekday, a blank pair meaning the day is off) and PlantHoliday (closures by name and date). These define the calendar every date is computed against, so they deserve ten careful minutes.

Auto-create is on by default, so a routing file naming a resource that has not been imported yet creates it on the fly. That is a useful safety net and a poor strategy: an auto-created work center has a name and nothing else, meaning one machine, no shift assignment, and no efficiency. Load the resource file properly first.

Items to Product

Only the identifier is required. Everything else can arrive later through a second, narrower refresh file, because blank cells preserve existing values on an update run. Watch identifier formatting across exports: matching ignores case but not leading zeros, so make every export render the item number the same way.

Resources to Workcenter

This is the file where scheduling accuracy is won or lost, because it carries capacity.

Number_Of_Instances is the highest-value column on the page. Syteline often models a resource as a capacity figure rather than a count of machines, so this is a column you set deliberately. A resource of four identical machines imported with one instance produces a plan roughly four times too long, and it fails quietly: nothing errors, the dates are simply wrong. The arithmetic is in how EDGEBIC calculates work center capacity.

If your export expresses capacity as an available-hours figure that already embeds a machine count, do not carry that number into Capacity unchanged while also setting instances, or you will count the same capacity twice. Instances plus the shift calendar is the representation the engine reasons about best.

Resource groups map to work center groups

Syteline groups resources; EDGEBIC models an interchangeable pool as a work center group. A routing step bound to a group re-evaluates every member on each reschedule, picks by strategy (earliest completion, primary first, or earliest start), and applies a per-member efficiency factor so a slower machine is chosen only when it still finishes first. Operations already started keep the machine they started on, because recorded work is never moved. The membership does not fit in an export column: import the members as ordinary work centers, then create the group inside EDGEBIC and add them. See how to create work center groups.

Current routings to BOR

Op_Flag is the field people get wrong first. True means "this row is an operation running on a resource". False means "this row is a component consumed at this point in the routing". Mixing them produces a routing full of resources that are actually parts, and it is visible immediately in the graphical designer.

Why the import takes two passes

A routing cannot be written row by row, because step 10 must point at step 20 and step 20 does not exist yet. So the import runs in two passes. Pass one validates each row, resolves or creates the items and resources it names, and buffers the row. Pass two groups the buffer by end item, sorts by sequence number, writes the steps, and wires the chain: 10 to 20, 20 to 30, and the terminal step to the finished item. Check that visually after the first import: a routing missing its final link draws as a chain floating free of the item it builds.

All of one item's steps must travel in one file, because a run wipes and recreates that item's steps on first reference. And re-importing is safe for running orders, because every scheduled job carries a frozen snapshot of the routing it was planned with.

Outside processing maps cleanly as an operation row on a resource that represents the vendor, with the turnaround expressed as transit days, so the outside time stays visible on the Gantt rather than buried inside one long step.

Job orders to SalesOrder

Two mask options control the date logic when the export carries only one date: one treats the job date as the due date, the other derives the job date backward from the due date. Choose the one matching how your export is built, once, on the mask. The mechanism is the same as forward versus backward scheduling.

Labor transactions to Actuals

Job number, work center id, and actual date are mandatory. Hours and pieces are both optional, and either can be derived from the other using the operation's rate. A Complete column marks the operation finished, and an explicit start column overrides the default of using the earliest imported date. The import always overwrites the days a file carries, so re-running a corrected extract fixes the numbers rather than doubling them. Actuals import last, because each row has to find an operation on a job that is already scheduled.

Conversions, blanks, and zeros

Reading the outcomes

Every row resolves to Created, Updated, Reused, or Failed. Reused is the default for a record that already exists, so a weekly item file of 9,000 rows reporting Created 15, Reused 8,985 is the desired result rather than a failure. When counts look wrong, the per-run log file carries one line per row with the exact reason for every failure.

What import cannot bring, and why it matters

The settings that most differentiate a schedule have no column in a Syteline export: the sequence-dependent setup matrix, operator skills and certifications, work center group strategies, bottleneck anchoring, and lot streaming transfer batches. Those are configured once in EDGEBIC and then apply to every imported order afterwards. The EDGEBIC product overview maps the engine, and the ERP integration architecture explains why one mask design serves every ERP, including the rest of the Infor family.

For the questions that come up before a project starts, see the Syteline integration FAQ. The Odoo and QuickBooks references show how the method changes across the ERP spectrum, and the ERP scheduling add-on page frames the category.