ERP integration

Orders from abas, utilisation back to sales.

A special machine builder running abas ERP manages customer orders, costing and production in the ERP. Whether design and assembly can take another order in the second quarter is answered by capacity planning in Linetrack. Through the REST API, abas orders become projects. Net capacity and planned hours per resource group and month flow back to where delivery dates are promised.

Via the REST APICustomer order becomes projectMonthly utilisation backConnected via middleware

abas ERP website ↗

In short

abas ERP is connected through the Linetrack REST API. A middleware such as n8n, Make or Power Automate, an integration tool such as abas Connect, or your abas partner reads customer orders, customers, suppliers and employees from abas and creates projects from templates in Linetrack. Utilisation per resource group and month with net capacity, planned hours and difference, KPIs per project and, if wanted, planned hours per task go back to abas.

Building blocks

What abas delivers and what comes back

For the capacity question Linetrack needs little from abas: the order, its delivery date and the people. The project manager plans the rest, and the result goes back to the ERP as figures.

To LinetrackOrder

A project from the customer order

For every customer order in abas that should trigger a project, the interface creates one in Linetrack from the matching template, such as “Special machine with controls” or “Retrofit on site”. The start date from abas sets the plan and the dates follow the project calendar.

  • Order number
  • Item number
  • Customer
  • Project manager
  • Portfolio
  • Template
  • Start date

Where in Linetrack: project overview

To LinetrackDate

Delivery date as a milestone

The delivery date agreed with the customer is a milestone in the project. If it changes in abas, the interface updates it by its ERP ID. In the Gantt the project manager sees whether design release, assembly and acceptance still fit before it.

  • Milestone
  • Delivery date
  • ERP ID
  • Status
To LinetrackStaff

Employees and absences

Employees arrive by personnel number from abas or the connected HR system, holidays and assembly assignments as absences with their type. If a designer is away for three weeks, the net capacity of their group drops by exactly that time.

  • Personnel number
  • Short code
  • Holiday
  • Sickness
  • Assembly
  • Training

Where in Linetrack: resource view

To LinetrackProperties

Assembly and cost centre as a reference

An assembly number, the cost centre or a link to the order in abas comes in as a property on the project or task. The bill of materials and MRP stay in abas; Linetrack plans the work on the machine, not its material.

  • Assembly number
  • Cost centre
  • Budget
  • Link
BackCapacity

Utilisation per resource group and month

Linetrack delivers net capacity, planned hours and difference per resource group and month. Your abas partner can build a report from this that shows, next to the order backlog, in which month mechanical design, electrical design or assembly is overbooked.

  • Resource group
  • Month
  • Net capacity
  • Planned hours
  • Difference
BackProject

Project status for the order meeting

Per project, completion, traffic light, phase, open and overdue tasks and schedule adherence come back with order and item number. In the weekly order meeting the status of every project is already in the ERP.

  • Completion
  • Traffic light
  • Phase
  • Schedule adherence
  • Overdue tasks

Day to day with abas

Where the figures from Linetrack are needed

Enquiry for a second test rig

An existing customer wants a second test rig, delivered in the autumn. Before sales writes the quotation with a delivery date, they check the utilisation report: electrical design is full until August, assembly is free in September. The date in the quotation is one the departments can actually keep.

The supplier is on the project

Purchasing creates the supplier for the conveyor system in abas. In Linetrack it appears with supplier number and contacts as a project partner, assigned to the project. Before installation on site, the assembly manager finds the right contact without asking purchasing.

An assembly assignment in the utilisation

Three fitters are commissioning at a customer's site in Poland in June, and the assignment is an absence of type Assembly in Linetrack. Their hours are missing from workshop assembly for that month, and the next report in abas shows the shortfall before another order is pushed into June.

Process

Three steps from abas order to project

  1. 1

    Set the rule

    Together we decide which orders in abas need a project, for example only orders with a design share, and which Linetrack template applies to each.

  2. 2

    Build the route

    Your middleware or abas partner reads the orders from abas and calls the Linetrack API with its own API key, triggered on a schedule or by an event in the ERP.

  3. 3

    Back into the report

    On a schedule, the same route fetches utilisation and project KPIs from Linetrack and writes them to abas. Every call is recorded in the Linetrack API log.

FAQ

Frequently asked questions

Any questions?

Book a call with our team.

Does Linetrack have a ready-made abas interface?

We do not have a ready-made abas adapter. The connection runs through the Linetrack REST API. We are glad to work out with you which data abas provides for it and whether your abas partner or a middleware builds the route.

Can sales see utilisation without opening Linetrack?

Yes, once utilisation per resource group and month is written back to abas. Anyone working in Linetrack finds the same values in the KPI dashboard, exportable as an Excel file with a chart.

Which orders become projects?

You decide. One option is a rule by order type or a flag on the order in abas that the middleware evaluates. Spare-part and service orders without design work then stay outside Linetrack.

How current are the figures that arrive in abas?

As current as the last fetch. The route collects the values, for example, every night or before the weekly sales meeting, and each fetch returns the planning status at that moment.

The platforms and brands mentioned belong to their respective owners. Mentioning them describes the technical connection and does not imply a partnership or certification.